Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

FileID logging

Specifying the FileID log entry type turns on logging for file opening, file closing, and error messages that do not contain the filename. Regarding the latter, there are a few OpenEdge error messages that indicate a problem in accessing a file, but do not show the filename in the message. The message only shows a FileID number. This makes it rather difficult to diagnose the problem. If you turn on FileID logging, OpenEdge will write a log entry that will show both the filename and ID just before it displays the error message. It might be useful to use this feature for other purposes as well. It might reveal inefficiencies in your 4GL code (opening an closing a file too many times), indicate why something is not working because the wrong file is being accessed (PROPATH or PATH problems), or provide insight if you have exceeded the limit on the number of open files. Information is logged at logging level 2 (Basic) and higher.

Log entries generated for this type contain the tag FILEID. An example of FileID logging messages (with headers suppressed) is shown:

FILEID Open d:\temp\program.r ID=30 FILEID Close d:\temp\program.r ID=30 FILEID Error 219 for file d:\temp\srt01934 ID=30

You also can turn on this logging at run time, by using the LOG-MANAGER system handle. For example, you can include the following line in the 4GL code:

LOG-MANAGER:LOG-ENTRY-TYPES = "FileID"

You can turn off this logging in the 4GL application by resetting the attribute. For example:

LOG-MANAGER:LOG-ENTRY-TYPES = ?